Eye tracker design for a wearable device

ABSTRACT

According to an aspect, a method for designing an eye tracker on a wearable device includes selecting a first three-dimensional (3D) model of at least a head of a person, selecting a second 3D model of a wearable device, positioning a synthetic eye within the first 3D model, positioning an eye tracker component at a first location on the second 3D model, the eye tracker component including at least one of an eye tracker sensor or a light source, moving at least one of the first 3D model or the second 3D model such that at least a portion of the first 3D model contacts at least a portion of the second 3D model, and generating performance data with the eye tracker component positioned at the first location on the second 3D model.

TECHNICAL FIELD

This description generally relates to eye tracker design for a wearabledevice, and, in particular to, positioning one of more eye trackercomponents on a wearable device that can increase the accuracy of an eyetracker across a number of users.

BACKGROUND

Wearable devices may include head-mounted devices (e.g., smartglasses,augmented reality (AR) devices, etc.), earbuds, watches, fitnesstrackers, cameras, body sensors, etc. A wearable device may include aneye tracker that can track a position of a person's eye, which can beused as an input for one or more applications of the wearable device.

SUMMARY

According to an aspect, a wearable device design system includes atleast one processor and a non-transitory computer-readable mediumstoring executable instructions that when executed by the at least oneprocessor cause the at least one processor to select a firstthree-dimensional (3D) model of at least a head of a person from a headsample database, select a second 3D model of a wearable device from awearable device database, position a synthetic eye within the first 3Dmodel, position an eye tracker sensor at a first location on the second3D model, move at least one of the first 3D model or the second 3D modelsuch that at least a portion of the second 3D model contacts at least aportion of the first 3D model, and generate performance data with theeye tracker sensor positioned at the first location on the second 3Dmodel, where the performance data includes information associated withperformance of an eye tracker using the synthetic eye.

According to some aspects, the wearable device design system may includeone or more of the following features (or any combination thereof). Theperformance data may include an amount of the synthetic eye that isvisible via the eye tracker sensor. The executable instructions includeinstructions that when executed by the at least one processor cause theat least one processor to move the eye tracker sensor from the firstlocation to a second location and re-generate the performance data withthe eye tracker sensor positioned at the second location. The executableinstructions include instructions that when executed by the at least oneprocessor cause the at least one processor to adjust a viewing angle ofthe eye tracker sensor and re-generate the performance data with the eyetracker sensor according to the adjusted viewing angle. The executableinstructions include instructions that when executed by the at least oneprocessor cause the at least one processor to adjust a synthetic eyeparameter of the synthetic eye model within the first 3D model. Thesynthetic eye parameter includes at least one of size of eye, size ofpupil, color of iris, shape of the iris or shape of cornea. Theexecutable instructions include instructions that when executed by theat least one processor cause the at least one processor to store theperformance data in a performance database, re-generate performance datafor other head samples in the head sample database, and identify alocation of the eye tracker sensor based on an analysis of theperformance database. The executable instructions include instructionsthat when executed by the at least one processor cause the at least oneprocessor to position a light source at a second location on the second3D model, where the performance data is generated with the eye trackersensor positioned at the first location and the light source positionedat the second location. /the second 3D model includes a prescriptionlens, where the executable instructions include instructions that whenexecuted by the at least one processor cause the at least one processorto adjust one or more parameters of the prescription lens The wearabledevice includes smartglasses configured to project a display, whereinthe eye tracker sensor is positioned on a frame of the smartglasses atthe first location.

According to an aspect, a method for designing an eye tracker on awearable device includes selecting a first three-dimensional (3D) modelof at least a head of a person from a head sample database, selecting asecond 3D model of a wearable device from a wearable device database,positioning a synthetic eye within the first 3D model, positioning aneye tracker component at a first location on the second 3D model, theeye tracker component including at least one of an eye tracker sensor ora light source, moving at least one of the first 3D model or the second3D model such that at least a portion of the first 3D model contacts atleast a portion of the second 3D model, and generating performance datawith the eye tracker component positioned at the first location on thesecond 3D model, where the performance data includes informationassociated with performance of an eye tracker using the synthetic eye.

According to some aspects, the method may include one or one of theabove/below features (or any combination thereof). The performance dataincludes an amount of the synthetic eye that is visible via the eyetracker sensor. The method may include adjusting a viewing angle of theeye tracker sensor and re-generating the performance data with the eyetracker sensor according to the adjusted viewing angle. The method mayinclude adjusting a synthetic eye parameter of the synthetic eye modelwithin the first 3D model, where the synthetic eye parameter includes atleast one of size of the synthetic eye, size of a pupil, shape or sizeof an iris, and/or color of the iris (and/or shape of cornea). Themethod may include storing the performance data in a performancedatabase, re-generating performance data for other head samples in thehead sample database, and identifying a location of the eye trackercomponent based on an analysis of the performance database. The methodmay include adjusting one or more parameters of prescription lensassociated with the wearable device.

According to an aspect, a non-transitory computer-readable mediumstoring executable instructions that when executed by at least oneprocessor cause the at least one processor to select a firstthree-dimensional (3D) model of at least a head of a person from a headsample database, select a second 3D model of a wearable device from awearable device database, position a synthetic eye within the first 3Dmodel, the synthetic eye being an eye-image having image datarepresenting a pupil, position an eye tracker sensor at a first locationon the second 3D model, move at least one of the first 3D model or thesecond 3D model such that at least a portion of the second 3D modelcontacts at least a portion of the first 3D model, and generateperformance data with the eye tracker sensor positioned at the firstlocation on the second 3D model, where the performance data includes anamount of the pupil of the synthetic eye that is visible via the eyetracker sensor.

According to some aspects, the non-transitory computer-readable mediummay include one or more of the following features (or any combinationthereof). The executable instructions include instructions that whenexecuted by the at least one processor cause the at least one processorto move the eye tracker sensor from the first location to a secondlocation and re-generate the performance data with the eye trackersensor positioned at the second location. The executable instructionsinclude instructions that when executed by the at least one processorcause the at least one processor to adjust a synthetic eye parameter ofthe synthetic eye model within the first 3D model, the synthetic eyeparameter including at least one of size of eye, size of pupil, color ofiris, or shape of the iris (and/or shape of cornea). The executableinstructions include instructions that when executed by the at least oneprocessor cause the at least one processor to store the performance datain a performance database, re-generate performance data for other headsamples in the head sample database, and identify a location of the eyetracker sensor based on an analysis of the performance database.

The details of one or more implementations are set forth in theaccompanying drawings and the description below. Other features will beapparent from the description and drawings, and from the claims.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1A illustrates a wearable device design system according to anaspect.

FIG. 1B illustrates a three-dimensional (3D) model associated with awearable device according to an aspect.

FIG. 2 illustrates a head-mounted display device according to an aspect.

FIGS. 3A through 3C illustrate a placement of a 3D model associated witha wearable device on a 3D model associated with a head sample accordingto an aspect.

FIG. 4 illustrates a flowchart depicting example operations of awearable device design system according to an aspect.

FIG. 5 illustrates example computing devices of the computing systemsdiscussed herein according to an aspect.

DETAILED DESCRIPTION

An eye tracker may include several components, which are located atcertain locations on the structure of the wearable device. However,different people have different head or facial features, where the eyetracking mechanism may have better accuracy on some people but lessaccuracy on other people. For example, a first person may wear awearable device that has an eye tracker, and the eye tracker mayproperly track the first person's eye movement. However, a second personmay wear the same wearable device, but the eye tracker may haveperformance issues with tracking the second person's eye movement (e.g.,the eye tracker's sensors may not be able to fully view the secondperson's eye). In some examples, it may be difficult to determine theposition of the individual components for an eye tracker that canoperate across a wide variety of users.

This disclosure relates to a wearable device design system configured todesign an eye tracker for use on a wearable device that can increase theperformance (e.g., accuracy) of the eye tracker across a number ofusers. In some examples, the wearable device includes a head-mounteddisplay device. In some examples, the wearable device includessmartglasses. An eye tracker is a device for measuring eye positionand/or eye movement. The eye tracker may include a plurality of eyetracker components that are positioned on the wearable device to enablethe eye tracker to measure the eye position and/or eye movement. The eyetracker components may include one or more eye tracker sensors and oneor more light sources. The eye tracker components may be positioned atdifferent locations on the wearable device. In the case of smartglasses,the eye tracker components may be positioned on different locations ofthe frame. The placement of the eye tracker components on the wearabledevice may affect the performance of the eye tracker.

The wearable device design system may determine the number and positionof the eye tracker components on the wearable device in a manner thatcan increase the performance of the eye tracker across a number (e.g., awide number) of users. For example, the wearable device design systemmay select a three-dimensional (3D) model representing at least a headof a person from a head model database. The head model database maystore 3D representations of a plurality of different head samples. Also,the wearable device design system may select a 3D model representing awearable device from a wearable device database. The wearable devicedatabase may store 3D representations of a plurality of wearable devices(e.g., different models of smartglasses). The wearable device designsystem includes a synthetic eye generator that generates and positions asynthetic eye within the head sample's 3D model. A synthetic eye may bea representation of an eye-image having visible features of a realisticeye such as a pupil, iris, cornea, and/or sclera.

The wearable device design system may position one or more eye trackercomponents on the wearable device's 3D model (e.g., programmatically orby a user). In some examples, a user may use a component placer toposition one or more eye tracker sensors and/or one or more lightsources on the wearable device's 3D model. The wearable device designsystem includes a sizing simulator that simulates a placement of thewearable device's 3D model on the head sample's 3D model. For example,the sizing simulator may receive the wearable device's 3D model and thehead sample's 3D model and then position the wearable device's 3D modelon the head sample's 3D model such that they contact each other. In someexamples, the sizing simulator may determine the contact points betweenthe wearable device's 3D model and the head sample's 3D model.

The wearable device design system generates performance data thatincludes information associated with an evaluation of the eye tracker.For example, the wearable device design system may evaluate an accuracyof the eye tracker with the eye tracker components positioned on thewearable device. The performance data may include any type of data thatindicates the accuracy of detecting and/or tracking the position of thesynthetic eyes. In some examples, the performance data includesinformation indicating an amount of the synthetic eye that is visiblevia the eye tracker sensor(s). For example, if the eye tracker sensor(s)is/are able to capture a substantial portion of the synthetic eye, theaccuracy of the eye tracker may be improved. In some examples, theperformance data includes signal levels such the presence (or level) ofdim spots, obstructions (e.g., clippings), and/or illumination levels.In some examples, the signal levels include a signal level relating toan obstruction between the camera and the eye, which can be caused byeyelashes or the angle of the camera having some part of the device(e.g., glasses) obstructing the field of view. In some examples, theperformance data includes the amount of eyelids (e.g., upper and/orlower) that is obstructing the iris/pupil. In some examples, the eyetracking evaluator may store the performance data in a performancedatabase.

The component placer may move the eye tracker components to differentlocations (e.g., programmatically or directed by the user), and thewearable device design system may re-generate the performance with theeye tracker components at the new locations. In some examples, thecomponent placer may adjust the viewing angle of one or more of the eyetracker sensors (e.g., programmatically or directed by the user) andre-generate the performance data using different viewing angles. In someexamples, the synthetic eye generator may adjust one or more syntheticeye parameters such as size of the synthetic eye, size of the pupil,shape/size of the iris, and/or color of the iris (and/or shape ofcornea). The wearable device design system may evaluate the performanceof the eye tracker using different values for the synthetic eyeparameters. In some examples, the wearable device includes prescriptionlens (e.g., corrective lens) and the component placer may be configuredto adjust the parameters of the prescription lens to meet differenttypes of prescriptions, and the wearable device design system mayevaluate the performance of the eye tracker using different lensparameters.

The wearable device design system is configured to select other headsamples from the head model database and generate performance data forthe eye tracker using the operations as described above. In someexamples, the wearable device design system is configured to analyze theperformance data in the database across the different head samples anddetermine the position (and/or viewing angle) of the eye tracker sensorsand/or light sources in a manner that increases the performance of theeye tracker across a plurality of head samples.

FIGS. 1A and 1B illustrate a wearable device design system 100 accordingto an aspect. The wearable device design system 100 is configured todesign an eye tracker 125 for use on a wearable device 114 that canincrease the performance (e.g., accuracy) of the eye tracker 125 acrossa number of users.

A wearable device 114 may include one or more devices, where at leastone of the devices is a display device capable of being worn on or inproximity to the skin of a person. The wearable device 114 may include ahead-mounted display (HMD) device such as an optical head-mounteddisplay (OHMD) device, a transparent heads-up display (HUD) device, anaugmented reality (AR) device, or other devices such as goggles orheadsets having sensors, display, and computing capabilities. However,the embodiments are not limited to head-mounted display devices, wherethe wearable device 114 may include any type of wearable device such asearbuds, watches, fitness trackers, cameras, body sensors, and/or anytype of computing device that can be worn on the skin of a person or inproximity to the skin of the person.

The wearable device 114 may include smartglasses. Smartglasses is anoptical head-mounted display device designed in the shape of a pair ofeyeglasses. For example, smartglasses are glasses that add information(e.g., project a display) alongside what the wearer views through theglasses. An example of a wearable device 114 configured as smartglassesis explained later in the disclosure with reference to FIG. 2. Thewearable device 114 includes a display (e.g., display 207 of FIG. 2)that is projected onto the field of view of the user. The display mayinclude a liquid crystal display (LCD), a light-emitting diode (LED)display, an organic light-emitting display (OLED), an electro-phoreticdisplay (EPD), or a micro-projection display adopting an LED lightsource. In some examples, the display may provide a transparent orsemi-transparent display such that the user wearing the glasses can seeimages provided by the display but also information located in the fieldof view of the smartglasses behind the projected images. In someexamples, this disclosure may refer to smartglasses, but the embodimentsmay be applied to other types of wearable computing devices and/orcombinations of mobile/wearable computing devices working together.

An eye tracker 125 is a device for measuring eye position and/or eyemovement. The eye tracker 125 can detect the presence, attention, and/orfocus of the user. In some examples, the eye tracker 125 can measure thepoint of gaze (e.g., where one is looking) and/or the motion of an eyerelative to the head. The eye tracker 125 may include a plurality of eyetracker components 130 that are positioned on the wearable device 114 toenable the eye tracker 125 to measure the eye position and/or eyemovement. The eye tracker components may include one or more eye trackersensors 138 and one or more light sources 140. The eye tracker sensor(s)138 may include camera(s) configured to capture image data. The lightsource(s) 140 may include light-emitting diode (LED)-based lightsources. Based on the information received via the eye tracker sensor(s)138, the eye tracker 125 is configured to measure eye position and trackits movement. The eye tracker components 130 may be positioned atdifferent locations on the wearable device 114. In the case ofsmartglasses, the eye tracker components 130 may be positioned ondifferent locations of the frame. However, the placement of the eyetracker components 130 on the wearable device 114 may affect theperformance of the eye tracker 125.

The wearable device design system 100 includes one or more processors144, which may be formed in a substrate configured to execute one ormore machine executable instructions or pieces of software, firmware, ora combination thereof. The processors 144 can besemiconductor-based—that is, the processors can include semiconductormaterial that can perform digital logic. The wearable device designsystem 100 can also include one or more memory devices 146. The memorydevices 146 may include any type of storage device that storesinformation in a format that can be read and/or executed by theprocessor(s) 144. The memory device(s) 146 may store executableinstructions that when executed by the processor(s) 144 cause theprocessor(s) 144 to perform any of the operations discussed herein. Thememory devices 146 may store one or more databases (e.g., head modeldatabase 106, wearable device database 112, performance database 118,etc.). In some examples, the memory device(s) 146 can store informationreceived or generated by the wearable device design system 100. In someexamples, the memory devices 146 may include applications and modules(e.g., model generator 104, data analyzer 122, eye tracking evaluator124, data selector 126, sizing simulator 132, synthetic eye generator134, component placer 136, etc.) that, when executed by the processor(s)144, perform the operations discussed herein. In some examples, theapplications and modules may be stored in an external storage device andloaded into the memory devices 146.

The wearable device design system 100 includes a data selector 126configured to communicate with a head model database 106 and a wearabledevice database 112. The head model database 106 may store a pluralityof 3D models 110 that correspond to a plurality of head samples 108.Each 3D model 110 corresponds to a separate head sample 108. The headmodel database 106 may store a wide variety of head samples 108 in theform of 3D models 110. A 3D model 110 includes 3D image data of at leasta head of a person. In some examples, the 3D models 110 were previouslycreated, and the 3D models 110 are incorporated into the head modeldatabase 106 to be used for designing an eye tracker 125 on a wearabledevice 114. In some examples, the wearable device design system 100includes a model generator 104 configured to create a 3D model 110 basedon image data 102. In some examples, the model generator 104 may receiveimage data 102 via one or more cameras and then create the 3D models110. The wearable device database 112 may store a plurality of 3D models116 that correspond to a plurality of wearable devices 114. Each 3Dmodel 116 corresponds to a separate wearable device 114. A 3D model 116includes 3D image data representing a particular wearable device 114. Insome examples, the 3D models 116 are different types (e.g., models,SKUs) of wearable devices 114.

The data selector 126 selects a 3D model 110 representing a head sample108 from the head model database 106 and selects a 3D model 116representing a wearable device 114 from the wearable device database112. In some examples, the data selector 126 may select the first headsample 108 from the head model database 106 (and then select other headsamples 108 after the first head sample 108 is evaluated). In someexamples, the data selector 126 may randomly select the head sample 108from the head model database 106. In some examples, the user mayinstruct the data selector 126 to select a particular head sample 108from the head model database 106. In some examples, the user instructsthe data selector 126 to select a particular wearable device 114. Insome examples, the data selector 126 may select a particular wearabledevice 114 and then generate performance data 120 for each of (or asubset of) of the head samples 108.

The wearable device design system 100 includes a synthetic eye generator134 that generates and positions synthetic eye(s) 128 within the 3Dmodel 110. For example, the 3D model 110 may not necessarily includeinformation that depicts the features of the eye of a particular headsample 108. However, the synthetic eye generator 134 may generate andposition synthetic eye(s) 128 within the 3D model 110 representing ahead sample 108. For example, a 3D center point of the eyeball may bederived from the 3D pupil positions (e.g., having a particular depth).The synthetic eye generator 134 may position the synthetic eye 128 intothe 3D model 110 such that a center of the synthetic eye 128 is placedinto the already existing eyeball center (e.g., derived from the 3Dpupil positions), and its pupil placed approximately in the pre-existingpupil location (e.g., with some deviation based on the various eyeballsizes that are simulated). A synthetic eye 128 may be a representationof an eye-image having visible features of a realistic eye such aspupil, iris, cornea, and/or sclera. In some examples, the synthetic eye128 is a 3D eyeball. In some examples, the synthetic eye 128 includesimage features representing eyelids and image features representingeyelashes. For example, the synthetic eye generator 134 may generatedifferent shapes and sizes of eyelids, which can affect the performanceof eye tracking. For example, eyelids and eye lashes and how they movewith gaze as part of the synthetic eye 128 may affect what aspects ofthe eye are visible. In some examples, the synthetic eye generator 134can vary the whiteness of the scleras, adding in darker spots and/orblood vessels. In some examples, the synthetic eye(s) 128 are positionedin the 3D model 110 at a location of the image data that represents aperson's eye(s). During the evaluation of the eye tracker 125, in someexamples, the synthetic eye generator 134 may adjust one or morefeatures of the synthetic eye 128 to determine the impact on the eyetracker's performance.

The wearable device design system 100 includes a component placer 136that positions one or more eye tracker components 130 on the 3D model116. For example, a user may use the component placer 136 to positionone or more eye tracker sensors 138 and/or one or more light sources 140on the 3D model 116. In some examples, the component placer 136 isconfigured to programmatically position one or more eye tracker sensors138 and/or one or more light sources 140 on the 3D model 116.

The wearable device design system 100 includes a sizing simulator 132that simulates a placement of the 3D model 110 with the positioned eyetracker components 130 on the 3D model 110 having the synthetic eyes128. The sizing simulator 132 may receive the 3D model 110 and the 3Dmodel 116 and then position the 3D model 116 on the 3D model 110 suchthat the 3D model 116 and the 3D model 110 contact each other. In someexamples, the sizing simulator 132 may move at least one of the 3D model110 or the 3D model 116 such that at least a portion of the 3D model 116contacts at least a portion of the 3D model 110. In some examples, aportion of the 3D model 110 contacting a portion of the 3D model 116 mayrefer to image data representing a surface in 3D model 110 at leastpartially intersects with image data representing a surface in 3D model116. In the case of smartglasses, in some examples, the sizing simulator132 may position the smartglasses on the face of the head sample wherethe frames contact the nose and fit behind the ears. In some examples,the smartglasses are positioned a certain distance away from the face,and the sizing simulator 132 may iteratively perform the followingoperations until convergence: tilt the smartglasses to rest on the ears,bend the smartglasses to clear the temples, move the smartglasses to thenose, and recenter the smartglasses to maintain contact with both sidesof the nose.

In some examples, the sizing simulator 132 places the glasses on thehead in the way they actually sit on the head, so therefore the view ofthe eye is not merely theoretical, but can be used to bypass the need toput glasses on real people's heads. Also, the sizing simulator 132 mayremove all the non-fit data, thereby avoiding eye tracking accommodationwhen the glasses would not fit the person anyway (e.g., too loose or tootight).

In some examples, the sizing simulator 132 may determine contact points(e.g., contact points 313 of FIGS. 3A through 3C) between the 3D model110 and the 3D model 116. The contact points may be the coordinates in3D space at which the 3D model 116 contacts the 3D model 110 when thewearable device 114 is placed on the head sample 108 (e.g., how thewearable device 114 can be worn on the head sample 108). In someexamples, the sizing simulator 132 uses one or more machine-learning(ML) models to predict the contact points. For example, the ML model maypredict the contact points based on the 3D model 110 and the 3D model116. In some examples, the contact points may be the points where thebridge portion (e.g., bridge portion 273 of FIG. 2) of the frame (e.g.,frame 271 of FIG. 2) of the wearable device 114 contacts the bridge ofthe person's nose, the points where the arm portions (e.g., arm portions274 of FIG. 2) of the wearable device 114 rest on the person's ears,and/or the points where the arm portions (e.g., arm portions 274 of FIG.2) contact the person's temples.

A ML model includes a neural network. The ML model may be aninterconnected group of nodes, each node representing an artificialneuron. The nodes are connected to each other in layers, with the outputof one layer becoming the input of a next layer. The ML model transformsan input, received by the input layer, transforms it through a series ofhidden layers, and produces an output via the output layer. Each layeris made up of a subset of the set of nodes. The nodes in hidden layersare fully connected to all nodes in the previous layer and provide theiroutput to all nodes in the next layer. The nodes in a single layerfunction independently of each other (i.e., do not share connections).Nodes in the output provide the transformed input to the requestingprocess. In some examples, the ML model is a convolutional neuralnetwork, which is a neural network that is not fully connected.Convolutional neural networks therefore have less complexity than fullyconnected neural networks. Convolutional neural networks can also makeuse of pooling or max-pooling to reduce the dimensionality (and hencecomplexity) of the data that flows through the neural network and thusthis can reduce the level of computation required. This makescomputation of the output in a convolutional neural network faster thanin neural networks.

In some examples, the sizing simulator 132 is configured to compute awearable fit value based on the simulation and/or contact points, wherethe wearable fit value represents a level of wearable fit of thewearable device 114 on the head of the person. In some examples, awearable fit value above a threshold level may indicate that thewearable device 114 can properly fit and be worn on the personrepresented by the 3D model 110.

In addition, in some examples, the sizing simulator 132 is configured tocompute the wearable fit value based on wearable fit parameters such aswhether the frame (e.g., frame 271 of FIG. 2) of the wearable device 114is wide enough to be comfortable with respect to the user's temples,whether the rim portions (e.g., rim portions 209 of FIG. 2) and bridgeportion (e.g., bridge portion 273 of FIG. 2) are sized so that thebridge portion (e.g., bridge portion 273 of FIG. 2) can rest comfortablyon the bridge of the user's nose, whether the arm portions (e.g., armportions 274) are sized to comfortably rest on the user's ears, andother such comfort related considerations. The calculation of thewearable fit value may also account for wearable fit parameters relatingto as-worn parameters including how the user naturally wears thewearable device 114, such as, for example, head posture/how the usernaturally holds his/her head, how the user positions the wearable device114 relative to his/her face, and the like. The calculation of thewearable fit value may also account for wearable fit parameters relatingto whether the size and/or shape and/or contour of the frame (e.g.,frame 271 of FIG. 2) is aesthetically pleasing to the user and iscompatible with the user's facial features.

The sizing simulator 132 may be configured to calculate a display fitvalue based on the simulation and/or contact points, where the displayfit value represents an amount of the display (e.g., display 207 of FIG.2) projected by the wearable device 114 that can be viewed by theperson. A display fit value above a threshold level may indicate thatthe display projected by the wearable device 114 can be substantiallyviewed by the user. In some examples, the sizing simulator 132 isconfigured to detect features such as pupil locations and ear saddlepoints based on the 3D model 110. The sizing simulator 132 is configuredto compute the display fit value using the contact points and otherdisplay fit parameters (or measurements) such as the pupil locations andear saddle points.

The wearable device design system 100 includes an eye tracking evaluator124 configured to generate performance data 120 that includesinformation associated with an evaluation of the eye tracker 125. Forexample, the eye tracking evaluator 124 may evaluate the accuracy of theeye tracker 125 with the eye tracker components 130 positioned on the 3Dmodel 116 of the wearable device 114. The performance data 120 mayinclude any type of data that indicates the accuracy of detecting and/ortracking the position of the synthetic eyes 128. In some examples, theperformance data 120 includes information indicating an amount of thesynthetic eye 128 that is visible via the eye tracker sensor(s) 138. Forexample, if the eye tracker sensor(s) 138 is/are able to capture asubstantial portion of the synthetic eye 128, the accuracy of the eyetracker 125 may be improved. In some examples, the performance data 120indicates the amount of pupil of the synthetic eye 128 that is visiblevia the eye tracker sensor(s) 138. In some examples, the performancedata includes signal levels such the presence (or level) of dim spots,obstructions (e.g., clippings), and/or illumination levels. In someexamples, the signal levels include a signal level relating to anobstruction between the camera and the eye, which can be caused byeyelashes or the angle of the camera having some part of the device(e.g., glasses) obstructing the field of view. In some examples, theperformance data includes the amount of eyelids (e.g., upper and/orlower) that is obstructing the iris/pupil. In some examples, the eyetracking evaluator 124 may store the performance data 120 in aperformance database 118.

The component placer 136 may move the eye tracker components 130 todifferent locations 150 (e.g., programmatically or directed by theuser), and the eye tracking evaluator 124 may re-generate theperformance data 120 with the eye tracker components 130 at the newlocations 150. In some examples, the component placer 136 may adjust theviewing angle 148 of one or more of the eye tracker sensors 138 (e.g.,programmatically or directed by the user) and the eye tracking evaluator124 may re-generate the performance data 120 using the different viewingangles 148. In some examples, the component placer 136 may add one ormore additional eye tracker sensors 138 and/or one or more light sources140 (e.g., programmatically or directed by the user), and the eyetracking evaluator 124 may evaluate the performance of the eye tracker125 with the additional eye tracker sensors 138 and/or light sources140.

Referring to FIGS. 1A and 1B, the component placer 136 may position aneye tracker sensor 138 at a location 150 a on the 3D model 116associated with the wearable device 114, and the eye tracking evaluator124 may generate performance data 120 with the eye tracker sensor 138 atthe location 150 a. Then, the user may use the component placer 136 toposition an eye tracker sensor 138 at a location 150 b on the 3D model,and the eye tracking evaluator 124 may re-generate performance data 120with the eye tracker sensor 138 at the location 150 b. In some examples,the component placer 136 may position a light source 140 at a location150 c on the 3D model 116 associated with the wearable device 114, andthe eye tracking evaluator 124 may generate performance data 120 withthe light source 140 at the location 150 c. Then, the component placer136 may move the light source 140 to a location 150 d, and the eyetracking evaluator 124 may re-generate the performance data 120 with thelight source 140 at the location 150 d.

In some examples, the synthetic eye generator 134 may adjust one or moresynthetic eye parameters 129 such as size of the synthetic eye 128, sizeof the pupil, shape/size of the iris, and/or color of the iris (shape ofcornea). In some examples, the synthetic eye generator 134 may adjustthe eyelids, eyelashes, or other parts associated with the synthetic eye128. The eye tracking evaluator 124 may evaluate the performance of theeye tracker 125 using different values for the synthetic eye parameters129. In the case of smartglasses, the wearable device 114 may includeprescription lens (e.g., corrective lens). The component placer 136 maybe configured to adjust the parameters of the lens to meet differenttypes of prescriptions, and the eye tracking evaluator 124 may evaluatethe performance of the eye tracker 125 using the different lensparameters. In some examples, the lens parameters may include thethickness of the lens and/or the curvature of the inner/outer lens ineither direction. In some examples, the lens parameters may includefeatures associated with bifocals and/or progressive prescriptionlenses.

In some examples, the wearable device design system 100 is configured toadjust one or more parameters associated with the display (e.g., display207 of FIG. 2) and evaluate its impact on the eye tracker 125. Forexample, the display may be associated with display optical parameters,such as properties of the waveguide, which could also be adjusted todetermine the impact of the waveguide on the eye tracker 125. Inaddition, properties of the display (e.g., display 207 of FIG. 2) mayinclude UI vector, display size, eyebox size, which may impact where theeye may be positioned relative to the eye tracker 125 and could be usedto inform design decisions and accommodation. For example, the wearabledevice design system 100 can adjust the UI vector, the display size,and/or the eyebox size, etc., and determine their impact on the eyetracker 125.

In some examples, the wearable device design system 100 is configured toselect other head samples 108 from the head model database 106 andgenerate performance data 120 for the eye tracker 125 using theoperations as describe above. For example, the data selector 126 mayselect another 3D model 110 from the head model database 106, and thesynthetic eye generator 134 may generate and position synthetic eyes 128within the 3D model 110. In some examples, the 3D model 116 that wasused in the previous iteration is used for the subsequent head sample108. The sizing simulator 132 may simulate the placement on the 3D model116 on the 3D model 110, and the eye tracking evaluator 124 may generateperformance data 120 using the new head sample 108. The user may use thecomponent placer 136 to adjust the location 150 and/or viewing angle 148of the eye tracker components 130. Also, the user may use the syntheticeye generator 134 to adjust the synthetic eye parameters 129. In someexamples, the wearable device design system 100 may generate performancedata 120 for all of the head samples 108 (or a subset thereof) in thehead model database 106.

In some examples, the wearable device design system 100 includes a dataanalyzer 122 configured to analyze the performance data 120 in theperformance database 118 across the different head samples 108. In someexamples, the data analyzer 122 may determine the location 150 andviewing angle 148 of the eye tracker components 130 such that theperformance of the eye tracker 125 is maximized across a number of headsamples 108. In some examples, the data analyzer 122 may identify thenumber of eye tracker components 130 and their locations 150 such thatthe amount of synthetic eye 128 (e.g., pupil) that is visible by the eyetrack sensors 138 is maximized.

FIG. 2 illustrates an example of a wearable device 214. The wearabledevice 214 may be an example of the wearable device 114 of FIGS. 1A and1B and may include any of the details discussed with reference to thosefigures.

In some examples, referring to FIG. 2, the wearable device 214 mayinclude smartglasses 296. Smartglasses 296 are glasses that addinformation (e.g., project a display 207) alongside what the wearerviews through the glasses. For example, the smartglasses 296 may includea display device 295 configured to project the display 207. In someexamples, the display device 295 may include a see-through near-eyedisplay. For example, the display device 295 may be configured toproject light from a display source onto a portion of teleprompter glassfunctioning as a beamsplitter seated at an angle (e.g., 30-45 degrees).The beamsplitter may allow for reflection and transmission values thatallow the light from the display source to be partially reflected whilethe remaining light is transmitted through. Such an optic design mayallow a user to see both physical items in the world, for example,through the lenses 272, next to content (for example, digital images,user interface elements, virtual content, and the like) generated by thedisplay device 295. In some implementations, waveguide optics may beused to depict content on the display device 295.

In some examples, instead of projecting information, the display 207 isan in-lens micro display. In some examples, the display 207 is referredto as an eye box. In some examples, smartglasses 296 (e.g., eyeglassesor spectacles), are vision aids, including lenses 272 (e.g., glass orhard plastic lenses) mounted in a frame 271 that holds them in front ofa person's eyes, typically utilizing a bridge portion 273 over the nose,and arm portions 274 (e.g., which may include temples or temple pieces)which rest over the ears. The bridge portion 273 may connect rimportions 209 of the frame 271. The smartglasses 296 include anelectronics component 270 that includes circuitry of the smartglasses296. In some examples, the electronics component 270 is included orintegrated into one of the arm portions 274 (or both of the arm portions274) of the smartglasses 296.

The smartglasses 296 can also include an audio output device (such as,for example, one or more speakers), an illumination device, a sensingsystem, a control system, at least one processor, and an outward facingimage sensor, or camera. In some examples, the smartglasses 296 mayinclude a gaze tracking device including, for example, one or moresensors, to detect and track eye gaze direction and movement. Datacaptured by the sensor(s) may be processed to detect and track gazedirection and movement as a user input. In some examples, the sensingsystem may include various sensing devices and the control system mayinclude various control system devices including, for example, one ormore processors operably coupled to the components of the controlsystem. In some implementations, the control system may include acommunication module providing for communication and exchange ofinformation between the wearable computing device and other externaldevices.

Referring to FIGS. 1A, 1B, and 2, the wearable device design system 100of FIGS. 1A and 1B may use a 3D model 116 of the smartglasses 296 ofFIG. 2 to identify the location of eye tracker components 130 on theframe 271 of the smartglasses 296. In some examples, the eye trackercomponents 130 may be positioned (and re-positioned) on the arm portions274, the rim portions 209, and/or the bridge portion 273. The wearabledevice design system 100 of FIGS. 1A and 1B may identify the location(s)150 and viewing angle(s) 148 of the eye tracker sensor(s) 138 and thelight source(s) 140 in a manner that can increase the accuracy of theeye tracker 125 across a number of different users.

FIGS. 3A through 3C illustrate an example output of a sizing simulator132 of FIGS. 1A and 1B. For example, a 3D model 316 of a wearable devicemay be positioned on a 3D model 310 of a head sample. The 3D model 316may be a 3D model of the smartglasses 296 of FIG. 2, which is configuredto project a display 307. Although not shown in FIGS. 3A through 3C, the3D model 310 includes synthetic eyes (e.g., synthetic eyes 128 of FIG.1A) positioned within the head sample. In some examples, as explainedabove, contact points 313 are predicted between the 3D model 310associated with at least a head of a person and a 3D model 316associated with a wearable device (e.g., smartglasses 296 of FIG. 2).The contact points 313 may be the coordinates in 3D space at which the3D model 316 contacts the 3D model 310 when the wearable device isplaced on the user's head. In some examples, the sizing simulator 132 ofFIGS. 1A and 1B generates a graphical representation of the placement,as shown in FIGS. 3A through 3C.

FIG. 4 illustrates a flowchart 400 depicting example operations of thewearable device design system 100 of FIGS. 1A and 1B. Although theflowchart 400 is described with reference to the wearable device designsystem 100 of FIGS. 1A and 1B, the flowchart 400 may be applicable toany of the embodiments herein. Although the flowchart 400 of FIG. 4illustrates the operations in sequential order, it will be appreciatedthat this is merely an example, and that additional or alternativeoperations may be included. Further, operations of FIG. 4 and relatedoperations may be executed in a different order than that shown, or in aparallel or overlapping fashion.

Operation 402 includes selecting a first three-dimensional (3D) model110 of at least a head of a person from a head sample database 106.Operation 404 includes selecting a second 3D model 116 of a wearabledevice 114 from a wearable device database 112. Operation 406 includespositioning a synthetic eye 128 within the first 3D model 110. Operation408 includes positioning an eye tracker sensor 138 at a first location150 a on the second 3D model 116. Operation 410 includes simulating aplacement of the second 3D model 116 on the first 3D model 110. In someexamples, the simulating includes moving at least one of the first 3Dmodel 110 or the second 3D model 116 such that the second 3D model 116contacts the first 3D model 110. Operation 412 includes generatingperformance data 120 with the eye tracker sensor 138 positioned at thefirst location 150 a on the second 3D model 116, where the performancedata 120 includes information associated with the performance of an eyetracker 125 using the synthetic eye 128.

FIG. 5 shows an example of an example computer device 500 and an examplemobile computer device 550, which may be used with the techniquesdescribed here. Computing device 500 includes a processor 502, memory504, a storage device 506, a high-speed interface 508 connecting tomemory 504 and high-speed expansion ports 510, and a low speed interface512 connecting to low speed bus 514 and storage device 506. Each of thecomponents 502, 504, 506, 508, 510, and 512, are interconnected usingvarious busses, and may be mounted on a common motherboard or in othermanners as appropriate. The processor 502 can process instructions forexecution within the computing device 500, including instructions storedin the memory 504 or on the storage device 506 to display graphicalinformation for a GUI on an external input/output device, such asdisplay 516 coupled to high speed interface 508. In otherimplementations, multiple processors and/or multiple buses may be used,as appropriate, along with multiple memories and types of memory. Inaddition, multiple computing devices 500 may be connected, with eachdevice providing portions of the necessary operations (e.g., as a serverbank, a group of blade servers, or a multi-processor system).

The memory 504 stores information within the computing device 500. Inone implementation, the memory 504 is a volatile memory unit or units.In another implementation, the memory 504 is a non-volatile memory unitor units. The memory 504 may also be another form of computer-readablemedium, such as a magnetic or optical disk.

The storage device 506 is capable of providing mass storage for thecomputing device 500. In one implementation, the storage device 506 maybe or contain a computer-readable medium, such as a floppy disk device,a hard disk device, an optical disk device, or a tape device, a flashmemory or other similar solid state memory device, or an array ofdevices, including devices in a storage area network or otherconfigurations. A computer program product can be tangibly embodied inan information carrier. The computer program product may also containinstructions that, when executed, perform one or more methods, such asthose described above. The information carrier is a computer- ormachine-readable medium, such as the memory 504, the storage device 506,or memory on processor 502.

The high speed controller 508 manages bandwidth-intensive operations forthe computing device 500, while the low speed controller 512 manageslower bandwidth-intensive operations. Such allocation of functions isexemplary only. In one implementation, the high-speed controller 508 iscoupled to memory 504, display 516 (e.g., through a graphics processoror accelerator), and to high-speed expansion ports 510, which may acceptvarious expansion cards (not shown). In the implementation, low-speedcontroller 512 is coupled to storage device 506 and low-speed expansionport 514. The low-speed expansion port, which may include variouscommunication ports (e.g., USB, Bluetooth, Ethernet, wireless Ethernet)may be coupled to one or more input/output devices, such as a keyboard,a pointing device, a scanner, or a networking device such as a switch orrouter, e.g., through a network adapter.

The computing device 500 may be implemented in a number of differentforms, as shown in the figure. For example, it may be implemented as astandard server 520, or multiple times in a group of such servers. Itmay also be implemented as part of a rack server system 524. Inaddition, it may be implemented in a personal computer such as a laptopcomputer 522. Alternatively, components from computing device 500 may becombined with other components in a mobile device (not shown), such asdevice 550. Each of such devices may contain one or more of computingdevices 500, 550, and an entire system may be made up of multiplecomputing devices 500, 550 communicating with each other.

Computing device 550 includes a processor 552, memory 564, aninput/output device such as a display 554, a communication interface566, and a transceiver 568, among other components. The device 550 mayalso be provided with a storage device, such as a microdrive or otherdevice, to provide additional storage. Each of the components 550, 552,564, 554, 566, and 568, are interconnected using various buses, andseveral of the components may be mounted on a common motherboard or inother manners as appropriate.

The processor 552 can execute instructions within the computing device550, including instructions stored in the memory 564. The processor maybe implemented as a chipset of chips that include separate and multipleanalog and digital processors. The processor may provide, for example,coordination of the other components of the device 550, such as controlof user interfaces, applications run by device 550, and wirelesscommunication by device 550.

Processor 552 may communicate with a user through control interface 558and display interface 556 coupled to a display 554. The display 554 maybe, for example, a TFT LCD (Thin-Film-Transistor Liquid Crystal Display)or an OLED (Organic Light Emitting Diode) display, or other appropriatedisplay technology. The display interface 556 may comprise appropriatecircuitry for driving the display 554 to present graphical and otherinformation to a user. The control interface 558 may receive commandsfrom a user and convert them for submission to the processor 552. Inaddition, an external interface 562 may be in communication withprocessor 552, so as to enable near area communication of device 550with other devices. External interface 562 may provide, for example, forwired communication in some implementations, or for wirelesscommunication in other implementations, and multiple interfaces may alsobe used.

The memory 564 stores information within the computing device 550. Thememory 564 can be implemented as one or more of a computer-readablemedium or media, a volatile memory unit or units, or a non-volatilememory unit or units. Expansion memory 574 may also be provided andconnected to device 550 through expansion interface 572, which mayinclude, for example, a SIMM (Single In Line Memory Module) cardinterface. Such expansion memory 574 may provide extra storage space fordevice 550 or may also store applications or other information fordevice 550. Specifically, expansion memory 574 may include instructionsto carry out or supplement the processes described above and may includesecure information also. Thus, for example, expansion memory 574 may beprovided as a security module for device 550 and may be programmed withinstructions that permit secure use of device 550. In addition, secureapplications may be provided via the SIMM cards, along with additionalinformation, such as placing identifying information on the SIMM card ina non-hackable manner.

The memory may include, for example, flash memory and/or NVRAM memory,as discussed below. In one implementation, a computer program product istangibly embodied in an information carrier. The computer programproduct contains instructions that, when executed, perform one or moremethods, such as those described above. The information carrier is acomputer- or machine-readable medium, such as the memory 564, expansionmemory 574, or memory on processor 552, that may be received, forexample, over transceiver 568 or external interface 562.

Device 550 may communicate wirelessly through communication interface566, which may include digital signal processing circuitry wherenecessary. Communication interface 566 may provide for communicationsunder various modes or protocols, such as GSM voice calls, SMS, EMS, orMMS messaging, CDMA, TDMA, PDC, WCDMA, CDMA2000, or GPRS, among others.Such communication may occur, for example, through radio-frequencytransceiver 568. In addition, short-range communication may occur, suchas using a Bluetooth, Wi-Fi, or other such transceiver (not shown). Inaddition, GPS (Global Positioning System) receiver module 570 mayprovide additional navigation- and location-related wireless data todevice 550, which may be used as appropriate by applications running ondevice 550.

Device 550 may also communicate audibly using audio codec 560, which mayreceive spoken information from a user and convert it to usable digitalinformation. Audio codec 560 may likewise generate audible sound for auser, such as through a speaker, e.g., in a handset of device 550. Suchsound may include sound from voice telephone calls, may include recordedsound (e.g., voice messages, music files, etc.) and may also includesound generated by applications operating on device 550.

The computing device 550 may be implemented in a number of differentforms, as shown in the figure. For example, it may be implemented as acellular telephone 580. It may also be implemented as part of a smartphone 582, personal digital assistant, or another similar mobile device.

Various implementations of the systems and techniques described here canbe realized in digital electronic circuitry, integrated circuitry,specially designed ASICs (application specific integrated circuits),computer hardware, firmware, software, and/or combinations thereof.These various implementations can include implementation in one or morecomputer programs that are executable and/or interpretable on aprogrammable system including at least one programmable processor, whichmay be special or general purpose, coupled to receive data andinstructions from, and to transmit data and instructions to, a storagesystem, at least one input device, and at least one output device. Inaddition, the term “module” may include software and/or hardware.

These computer programs (also known as programs, software, softwareapplications or code) include machine instructions for a programmableprocessor and can be implemented in a high-level procedural and/orobject-oriented programming language, and/or in assembly/machinelanguage. As used herein, the terms “machine-readable medium”“computer-readable medium” refers to any computer program product,apparatus and/or device (e.g., magnetic discs, optical disks, memory,Programmable Logic Devices (PLDs)) used to provide machine instructionsand/or data to a programmable processor, including a machine-readablemedium that receives machine instructions as a machine-readable signal.The term “machine-readable signal” refers to any signal used to providemachine instructions and/or data to a programmable processor.

To provide for interaction with a user, the systems and techniquesdescribed here can be implemented on a computer having a display device(e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor)for displaying information to the user and a keyboard and a pointingdevice (e.g., a mouse or a trackball) by which the user can provideinput to the computer. Other kinds of devices can be used to provide forinteraction with a user as well; for example, feedback provided to theuser can be any form of sensory feedback (e.g., visual feedback,auditory feedback, or tactile feedback); and input from the user can bereceived in any form, including acoustic, speech, or tactile input.

The systems and techniques described here can be implemented in acomputing system that includes a back end component (e.g., as a dataserver), or that includes a middleware component (e.g., an applicationserver), or that includes a front end component (e.g., a client computerhaving a graphical user interface or a Web browser through which a usercan interact with an implementation of the systems and techniquesdescribed here), or any combination of such back end, middleware, orfront end components. The components of the system can be interconnectedby any form or medium of digital data communication (e.g., acommunication network). Examples of communication networks include alocal area network (“LAN”), a wide area network (“WAN”), and theInternet.

The computing system can include clients and servers. A client andserver are generally remote from each other and typically interactthrough a communication network. The relationship of client and serverarises by virtue of computer programs running on the respectivecomputers and having a client-server relationship to each other.

In some implementations, the computing devices depicted in FIG. 5 caninclude sensors that interface with a virtual reality (VR headset 590).For example, one or more sensors included on a computing device 550 orother computing device depicted in FIG. 5, can provide input to VRheadset 590 or in general, provide input to a VR space. The sensors caninclude, but are not limited to, a touchscreen, accelerometers,gyroscopes, pressure sensors, biometric sensors, temperature sensors,humidity sensors, and ambient light sensors. The computing device 550can use the sensors to determine an absolute position and/or a detectedrotation of the computing device in the VR space that can then be usedas input to the VR space. For example, the computing device 550 may beincorporated into the VR space as a virtual object, such as acontroller, a laser pointer, a keyboard, a weapon, etc. Positioning ofthe computing device/virtual object by the user when incorporated intothe VR space can allow the user to position the computing device to viewthe virtual object in certain manners in the VR space. For example, ifthe virtual object represents a laser pointer, the user can manipulatethe computing device as if it were an actual laser pointer. The user canmove the computing device left and right, up and down, in a circle,etc., and use the device in a similar fashion to using a laser pointer.

In some implementations, one or more input devices included on, orconnected to, the computing device 550 can be used as input to the VRspace. The input devices can include, but are not limited to, atouchscreen, a keyboard, one or more buttons, a trackpad, a touchpad, apointing device, a mouse, a trackball, a joystick, a camera, amicrophone, earphones or buds with input functionality, a gamingcontroller, or other connectable input device. A user interacting withan input device included on the computing device 550 when the computingdevice is incorporated into the VR space can cause a particular actionto occur in the VR space.

In some implementations, a touchscreen of the computing device 550 canbe rendered as a touchpad in VR space. A user can interact with thetouchscreen of the computing device 550. The interactions are rendered,in VR headset 590 for example, as movements on the rendered touchpad inthe VR space. The rendered movements can control objects in the VRspace.

In some implementations, one or more output devices included on thecomputing device 550 can provide output and/or feedback to a user of theVR headset 590 in the VR space. The output and feedback can be visual,tactical, or audio. The output and/or feedback can include, but is notlimited to, vibrations, turning on and off or blinking and/or flashingof one or more lights or strobes, sounding an alarm, playing a chime,playing a song, and playing of an audio file. The output devices caninclude, but are not limited to, vibration motors, vibration coils,piezoelectric devices, electrostatic devices, light emitting diodes(LEDs), strobes, and speakers.

In some implementations, the computing device 550 may appear as anotherobject in a computer-generated, 3D environment. Interactions by the userwith the computing device 550 (e.g., rotating, shaking, touching atouchscreen, swiping a finger across a touch screen) can be interpretedas interactions with the object in the VR space. In the example of thelaser pointer in a VR space, the computing device 550 appears as avirtual laser pointer in the computer-generated, 3D environment. As theuser manipulates the computing device 550, the user in the VR space seesmovement of the laser pointer. The user receives feedback frominteractions with the computing device 550 in the VR space on thecomputing device 550 or on the VR headset 590.

In some implementations, one or more input devices in addition to thecomputing device (e.g., a mouse, a keyboard) can be rendered in acomputer-generated, 3D environment. The rendered input devices (e.g.,the rendered mouse, the rendered keyboard) can be used as rendered inthe VR space to control objects in the VR space.

Computing device 500 is intended to represent various forms of digitalcomputers, such as laptops, desktops, workstations, personal digitalassistants, servers, blade servers, mainframes, and other appropriatecomputers. Computing device 550 is intended to represent various formsof mobile devices, such as personal digital assistants, cellulartelephones, smart phones, and other similar computing devices. Thecomponents shown here, their connections and relationships, and theirfunctions, are meant to be exemplary only, and are not meant to limitimplementations of the inventions described and/or claimed in thisdocument.

A number of embodiments have been described. Nevertheless, it will beunderstood that various modifications may be made without departing fromthe spirit and scope of the specification.

In addition, the logic flows depicted in the figures do not require theparticular order shown, or sequential order, to achieve desirableresults. In addition, other steps may be provided, or steps may beeliminated, from the described flows, and other components may be addedto, or removed from, the described systems. Accordingly, otherembodiments are within the scope of the following claims.

What is claimed is:
 1. A wearable device design system comprising: atleast one processor; and a non-transitory computer-readable mediumstoring executable instructions that when executed by the at least oneprocessor cause the at least one processor to: select a firstthree-dimensional (3D) model of at least a head of a person from a headsample database; select a second 3D model of a wearable device from awearable device database; position a synthetic eye within the first 3Dmodel; position an eye tracker sensor at a first location on the second3D model; move at least one of the first 3D model or the second 3D modelsuch that at least a portion of the second 3D model contacts at least aportion of the first 3D model; and generate performance data with theeye tracker sensor positioned at the first location on the second 3Dmodel, the performance data including information associated withperformance of an eye tracker using the synthetic eye.
 2. The wearabledevice design system of claim 1, wherein the performance data includesan amount of the synthetic eye that is visible via the eye trackersensor.
 3. The wearable device design system of claim 1, wherein theexecutable instructions include instructions that when executed by theat least one processor cause the at least one processor to: move the eyetracker sensor from the first location to a second location; andre-generate the performance data with the eye tracker sensor positionedat the second location.
 4. The wearable device design system of claim 1,wherein the executable instructions include instructions that whenexecuted by the at least one processor cause the at least one processorto: adjust a viewing angle of the eye tracker sensor; and re-generatethe performance data with the eye tracker sensor according to theadjusted viewing angle.
 5. The wearable device design system of claim 1,wherein the executable instructions include instructions that whenexecuted by the at least one processor cause the at least one processorto: adjust a synthetic eye parameter of the synthetic eye model withinthe first 3D model.
 6. The wearable device design system of claim 5,wherein the synthetic eye parameter includes at least one of size ofeye, size of pupil, color of iris, shape of the iris or shape of cornea.7. The wearable device design system of claim 1, wherein the executableinstructions include instructions that when executed by the at least oneprocessor cause the at least one processor to: store the performancedata in a performance database; re-generate performance data for otherhead samples in the head sample database; and identify a location of theeye tracker sensor based on an analysis of the performance database. 8.The wearable device design system of claim 1, wherein the executableinstructions include instructions that when executed by the at least oneprocessor cause the at least one processor to: position a light sourceat a second location on the second 3D model, wherein the performancedata is generated with the eye tracker sensor positioned at the firstlocation and the light source positioned at the second location.
 9. Thewearable device design system of claim 1, wherein the second 3D modelincludes a prescription lens, wherein the executable instructionsinclude instructions that when executed by the at least one processorcause the at least one processor to: adjust one or more parameters ofthe prescription lens.
 10. The wearable device design system of claim 1,wherein the wearable device includes smartglasses configured to projecta display, wherein the eye tracker sensor is positioned on a frame ofthe smartglasses at the first location.
 11. A method for designing aneye tracker on a wearable device, the method comprising: selecting afirst three-dimensional (3D) model of at least a head of a person from ahead sample database; selecting a second 3D model of a wearable devicefrom a wearable device database; positioning a synthetic eye within thefirst 3D model; positioning an eye tracker component at a first locationon the second 3D model, the eye tracker component including at least oneof an eye tracker sensor or a light source; simulating a placement ofthe second 3D model on the first 3D model such that wearable device ispositioned on the head of the person; and generating performance datawith the eye tracker component positioned at the first location on thesecond 3D model, the performance data including information associatedwith performance of an eye tracker using the synthetic eye.
 12. Themethod of claim 11, wherein the performance data includes an amount ofthe synthetic eye that is visible via the eye tracker sensor.
 13. Themethod of claim 11, further comprising: adjusting a viewing angle of theeye tracker sensor; and re-generating the performance data with the eyetracker sensor according to the adjusted viewing angle.
 14. The methodof claim 11, further comprising: adjusting a synthetic eye parameter ofthe synthetic eye model within the first 3D model, the synthetic eyeparameter including at least one of eyelids or eyelashes.
 15. The methodof claim 11, further comprising: storing the performance data in aperformance database; re-generating performance data for other headsamples in the head sample database; and identifying a location of theeye tracker component based on an analysis of the performance database.16. The method of claim 11, further comprising: adjusting one or moreparameters of prescription lens associated with the wearable device. 17.A non-transitory computer-readable medium storing executableinstructions that when executed by at least one processor cause the atleast one processor to: select a first three-dimensional (3D) model ofat least a head of a person from a head sample database; select a second3D model of a wearable device from a wearable device database; positiona synthetic eye within the first 3D model, the synthetic eye being aneye-image having image data representing a pupil; position an eyetracker sensor at a first location on the second 3D model; move at leastone of the first 3D model or the second 3D model such that at least aportion of the second 3D model contacts at least a portion of the first3D model; and generate performance data with the eye tracker sensorpositioned at the first location on the second 3D model, the performancedata including an amount of the pupil of the synthetic eye that isvisible via the eye tracker sensor.
 18. The non-transitorycomputer-readable medium of claim 17, wherein the executableinstructions include instructions that when executed by the at least oneprocessor cause the at least one processor to: move the eye trackersensor from the first location to a second location; and re-generate theperformance data with the eye tracker sensor positioned at the secondlocation.
 19. The non-transitory computer-readable medium of claim 17,wherein the executable instructions include instructions that whenexecuted by the at least one processor cause the at least one processorto: adjust a synthetic eye parameter of the synthetic eye model withinthe first 3D model, the synthetic eye parameter including at least oneof size of eye, size of pupil, color of iris, or shape of the iris. 20.The non-transitory computer-readable medium of claim 17, wherein theexecutable instructions include instructions that when executed by theat least one processor cause the at least one processor to: store theperformance data in a performance database; re-generate performance datafor other head samples in the head sample database; and identify alocation of the eye tracker sensor based on an analysis of theperformance database.